Maintenance of subscriber history for service support applications in an IP-based telecommunications system

ABSTRACT

A facility for maintaining a subscriber history pertaining to the use of a mobile device with an IP-based telecommunications service offered by a service provider. When a connection request is made by a mobile device to access an IP-based telecommunications service, one or more identifiers associated with the requesting mobile device and access point are provided in the request and stored by the facility. In some cases, the identifiers are stored even if the mobile device is unable to, or not authorized to, access the telecommunications service. Additional parameters associated with the request from the mobile device, such as a time stamp and details of a subsequent telecommunications session, are also associated with the stored request. The history of requests to access the IP-based telecommunications service from the mobile device are maintained by the facility and provided to a service support provider.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 11/552,096, filed on Oct. 23, 2006, and entitled“MAINTENANCE OF SUBSCRIBER HISTORY FOR SERVICE SUPPORT APPLICATIONS INAN IP-BASED TELECOMMUNICATIONS SYSTEM,” now U.S. Pat. No. 8,351,420,which is hereby incorporated herein in its entirety by reference.

BACKGROUND

A variety of technologies enable telecommunication services to beoffered using Internet Protocol (IP). Commonly referred to as Voice overIP, or VoIP, such technologies enable telecommunications on any publicor private IP network, including the Internet. VoIP technology permits auser to receive IP-based telecommunications services through a varietyof devices, including a desktop computer, a notebook computer, an analoghandset used in conjunction with a VoIP telephone adapter, aVoIP-enabled handset, or other like device.

Increasingly, mobile devices, such as notebook computers, personaldigital assistants (PDAs), wireless handhelds, wireless handsets, orother similar devices, are also being enabled to receive IP-basedtelecommunications services. Such services are provided by enabling themobile device to communicate with a wireless router and access anyIP-based wireless access network, such as a network based on the IEEE802.16 (WiMAX), IEEE 802.20 Mobile Broadband Wireless Access (MBWA),Ultra Wideband (UWB), 802.11 wireless fidelity (Wi-Fi), and Bluetoothstandards.

Moreover, dual-mode mobile telecommunications devices may be enabled tocommunicate with any IP-based wireless access network. For instance,Unlicensed Mobile Access (UMA) technology allows wireless serviceproviders to merge cellular networks, such as Global System for MobileCommunications (GSM) networks, and IP-based wireless networks into oneseamless service with one mobile device, one user interface, and acommon set of network services for both voice and data. UMA technologyhas recently been accepted into release 6 of the 3rd GenerationPartnership Project (3GPP) standard as a General Access Network (GAN).

With UMA solutions, subscribers may move between cellular networks andIP-based wireless networks with seamless voice and data sessioncontinuity as transparently as they move between cells within thecellular network. Seamless in-call handover between the IP-basedwireless network and cellular network ensures that the user's locationand mobility do not affect the services delivered to the user. Servicesmay be identical whether connected over the IP-based wireless network orthe cellular network. UMA technology effectively creates a parallelradio access network, the UMA network, which interfaces to the mobilecore network using standard mobility-enabled interfaces. The mobile corenetwork remains unchanged. The common mobile core network makes itpossible for the service provider to take advantage of full service andoperational transparency. For example, the existing service providerBusiness Support Systems (BSS), service delivery systems, contentservices, regulatory compliance systems, and Operation Support Systems(OSS) can support the UMA network with little or no change. Serviceenhancements and technology evolution of the mobile core network applytransparently to both cellular access and UMA.

Although IP-based telecommunications technologies offer substantialbenefits to users of the technology, service providers face manyobstacles to the widespread use of these technologies. One of thechallenges facing any service provider that launches an IP-basedtelecommunications service is service support. Service support includescustomer care operations, service diagnostic operations, and relatedoperations. Service support issues are particularly challenging in anIP-based telecommunications network because the service providertypically does not have end-to-end control of the network used by asubscriber. Instead, any communications between mobile devices used bysubscribers and the network systems of the service provider may involvesome transit over third-party broadband networks and the Internet. Sincethe third-party networks and the Internet are not under the control ofthe service provider, diagnosing service problems is particularlycomplicated. Performance problems may result from problems in one ormore components that make up the service provider network, thethird-party network, and/or the Internet. In order to providesubscribers with a high quality of service and diagnose service problemsas quickly as possible, it is therefore important that service providersimplement a robust service support solution that allows service supportrepresentatives to quickly and easily troubleshoot service problems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example Voice over IP system.

FIGS. 2A and 2B illustrate example converged wireless network systemsthat combine cellular networks with IP-based wireless telecommunicationsnetworks.

FIG. 3 illustrates a network controller configured in an IP-basedtelecommunications network to authorize or reject access to the networkbased on various identifiers.

FIG. 4 is a flow chart of a registration process used by a mobile deviceto access an IP-based telecommunications network.

FIG. 5 is a subscriber history table stored by the IP-basedtelecommunications system and accessible by a service support provider.

FIG. 6 is a flow chart of a method for determining the proper IP-basedtelecommunications service zone and CGI that are associated with amobile device.

FIG. 7 is a screenshot of a representative interface for accessing asubscriber history in a VoIP system.

DETAILED DESCRIPTION

A software and/or hardware facility is disclosed for maintaining asubscriber history pertaining to the use of a mobile device with anIP-based telecommunications network, including but not limited toIP-based telecommunications networks converged with cellulartelecommunications networks (such as a UMA service). When a connectionrequest is made by a mobile device to access an IP-based wirelesstelecommunications network, one or more identifiers associated with therequesting mobile device and access point are provided in the request.The identifiers associated with the requesting mobile device and accesspoint are stored by the facility. In some cases, the identifiers arestored even if the mobile device is unable to, or not authorized to,fully access the IP-based telecommunications service. Additionalparameters associated with the request from the mobile device, such as atime stamp and details of a subsequent session, are also associated withthe stored request. The history of requests to access the IP-basedtelecommunications service from the mobile device are maintained by thefacility and provided to a service support provider. By using the accesshistory, a service support provider may be able to quickly and easilyresolve service problems such as a subscriber's inability to access theIP-based service via their mobile device.

In some embodiments of the facility, a service support interface isprovided to allow service support personnel to easily review thesubscriber history. The interface highlights groups of connectionrequests that failed, and allows the history to be sorted using avariety of sort keys. Service support personnel are thereby able toquickly focus on areas of potential problems and troubleshoot toidentify service solutions.

In some embodiments of the facility specific to a converged network, thesubscriber history is updated by the facility when more accurateinformation pertaining to some or all of the identifiers in theconnection request becomes available. For example, one of theidentifiers in a connection request may be a cell global identifier(CGI), or an identifier associated with a cell (GSM, CDMA or other) thatthe mobile device has previously accessed or is able to access whenmaking the request to access the IP-based telecommunication service.Since the CGI may be used by the service provider for certain billingissues, the CGI associated with the connection request in the mobiledevice history may be updated by the service provider if a preferred CGIvalue is identified by the service provider.

The following description provides specific details for a thoroughunderstanding of, and enabling description for, various embodiments ofthe technology. One skilled in the art will understand that thetechnology may be practiced without these details. In some instances,well-known structures and functions have not been shown or described indetail to avoid unnecessarily obscuring the description of theembodiments of the technology. It is intended that the terminology usedin the description presented below be interpreted in its broadestreasonable manner, even though it is being used in conjunction with adetailed description of certain embodiments of the technology. Althoughcertain terms may be emphasized below, any terminology intended to beinterpreted in any restricted manner will be overtly and specificallydefined as such in this Detailed Description section.

I. Example VoIP and UMA Networks

FIG. 1 illustrates the components of a generalized Voice over InternetProtocol (VoIP) system 10 for mobile communication devices. The systemcomprises one or more access points (APs) 15 that can acceptcommunications 20 from mobile devices 25. The access point includes awireless router 30 and a broadband modem 35 that enable connection to anInternet Protocol (IP) network 40. IP network 40 may be one or morepublic networks, private networks, or combination of public and privatenetworks. IP packets that carry communications from the mobile device 25are received at the access point 15 and transported through the IPnetwork 40 to a signaling gateway 45. Signaling gateway 45 is typicallyoperated by a service provider and converts the VoIP signal to atraditional phone service signal. The phone signal is then conveyed tothe intended recipient via a public switched telephone network (PSTN)50. A call controller 55 that is located in the service provider'snetwork provides call logic and call control functions. An applicationserver 60 that is located in the service provider's network provideslogic and execution of one or more applications or services that areoffered by the server provider, such as implementing various access andsecurity rules.

The VoIP system depicted in FIG. 1 is an architecture that broadlyenables any mobile device to receive IP-formatted telecommunicationservices. One application of that technology is Unlicensed Mobile Access(UMA) technology, which allows cellular service providers to offer theirproducts and services seamlessly over Internet-connected broadbandnetworks. Mobile devices may utilize licensed spectrums (such asspectrums for cellular communications) and alternate licensed,semilicensed and unlicensed spectrums (such as spectrums that can beutilized for IP-based communication). For example, dual-mode cellularphones may access a cellular network, such as a GSM, CDMA, or othernetwork network, or an IP-based wireless network, such as a networkbased on the IEEE 802.16 (WiMAX), IEEE 802.20 Mobile Broadband WirelessAccess (MBWA), Ultra Wideband (UWB), 802.11 wireless fidelity (Wi-Fi),or Bluetooth standards. The IP-based networks are accessed via wirelessaccess points that are typically connected to a DSL (Digital SubscriberLine) modem, a cable modem, a satellite modem, or any other broadbandInternet connection. The access points may be open or closed, and may belocated in a subscriber's home, in public locations such as coffeeshops, libraries, or schools, or in corporate locations.

When a mobile device accesses an IP-based wireless network, informationis initially formatted in the device's native cellular protocol (such asGSM or CDMA protocols) and then encapsulated into Internet Protocol (IP)packets, transmitted to the access point, and communicated over theInternet to the cellular service provider's mobile core network. Suchtransmission bypasses the service provider's existing network of radiotowers. Because the same native cellular protocols are used incommunications involving IP access points as with traditional radiotowers, the cellular service provider maintains a large degree of systemcompatibility even though using an IP-based network. The systems of thecellular service provider that deliver content and handle mobility maynot even need to be aware that a subscriber's mobile device is on anIP-based network. The system may instead assume the mobile device is ona cellular network. The IP-based network is therefore abstracted withrespect to the cellular network, regardless of whether the mobile deviceconnects to the cellular network via a cell tower (for licensed spectrumaccess) or a wireless access point (for licensed, semilicensed andunlicensed spectrum access).

A non-exhaustive list of products and services available on IP-basednetworks includes not only voice services, but also supplementaryservices like call forwarding and call waiting, text messaging serviceslike SMS, and data-based services like ringtone downloads, gamedownloads, picture messaging, email and web browsing. Further, since amobile device is connected to an IP network, all manner of data servicesavailable over such networks may be provided to the mobile device.

FIG. 2A is an illustration of a system 100 that combines a cellulartelephone network with a IP-based wireless telecommunications network(e.g. a UMA network). The described system 100 accepts registrationrequests and communication connections from a mobile device 110 toeither a cellular telephone network or to an IP-based wirelesstelecommunications network.

The example cellular telephone network includes one or more cell towers120 that are configured to accept cellular communications 112 frommobile device 110. The cell towers 120 are connected to a controller(such as a base station controller/radio network controller (BSC/RNC))176 via a private network 130. The private network 130 can include avariety of connections such as T1 lines, a wide area network (WAN), alocal area network (LAN), various network switches, and other similarcomponents. Cell tower controller 176 controls network communicationtraffic to the carrier network 190, where all communications aremanaged. An example carrier network 190 includes a switch (such as amobile switching center (MSC)) 192, which is configured to controldata/call flows, perform load balancing, as well as other functions. Avariety of system databases may also be accessed in the carrier networksuch as, e.g., an operation support subsystem (OSS) database 194, abusiness support system (BSS) database 196, and a central subscriberdatabase that contains details of a carrier's subscribers (such as ahome location register (HLR)) 198, for billing, call logging, etc.

The example IP-based wireless telecommunications network includes one ormore access points (APs) 140 that can accept IP communications 114 frommobile device 110. An access point can be configured as part of awireless network in one or more locations such as a public network 142,a home network 144, or a private business network 146. Each access pointis coupled to an Internet Protocol (IP) network 150 through a broadbandconnection. IP packets that carry communications (data, voice, SMS,etc.) are routed from the access points to a security gateway (SGW) 171through the IP network 150. The security gateway controls access to thenetwork controller (NC) 166, which communicates with a database 168 forlogging and accessing various data associated with communications. Thenetwork controller 166 is also configured to manage access with thecarrier network 190 in a similar manner to that performed by the celltower controller 176.

Authentication of a request for access by a mobile device over theIP-based wireless telecommunications network is handled by the securitygateway 171, which communicates with an authentication, access andauthorization (AAA) module 172 as shown in FIG. 2A. Challenges andresponses to requests for access by the mobile device are communicatedbetween a central subscriber database 198 and the AAA module 172. Whenauthorization is granted, the security gateway 171 communicates theassignment of an IP address to the mobile device 110 that requestedaccess. Once the IP address is passed to the mobile device 110 by thesecurity gateway 171, the public IP address assigned to the device ispassed to the NC.

FIG. 2B illustrates another example system that combines a cellulartelephone network with an IP-based wireless telecommunications network.The described system 100′ accepts registration requests andcommunication connections from a mobile device 110 to either a cellulartelephone network (not shown) or to an IP-based wirelesstelecommunications network. The system 100′ includes one or more accesspoints (AP) 140 that accept communications 114 from mobile device 110.Each access point is coupled to an Internet Protocol network 150 througha broadband connection. IP network 150 routes communications (data,voice, SMS, etc.) between the access points and a security gateway (SGW)171. The security gateway 171 controls access to the network controller(NC) 166, which communicates with a database (not shown) for logging andaccessing various data associated with communications. Authentication,access, and authorization are handled by SGW 171 via AAA module 172, aspreviously described.

For the example system 100′, the path of a signaling communication isrouted through the network controller 166 to a mobile switching system(MSS) 180, while the voice bearer path is routed through the networkcontroller 166 to a media gateway (MGW) 182. The signaling portion of acommunication governs various overhead aspects of the communication suchas, for example, when the call starts, when the call stops, initiating atelephone ring, characteristics of the transmitted data, etc. The voicebearer portion of the communication contains the actual content (eitherdata or voice information) of the communication. The MGW 182 controlsthe content flow between the service provider and the mobile device 110,while the MSS 180 controls the signaling flow (or controlsoverhead-related flow) between the service provider and the mobiledevice 110.

FIG. 3 illustrates a configuration that utilizes a network controllerfor managing IP-based wireless telecommunications network authorization.A mobile device 110 initiates a connection request with a IP-basedwireless telecommunications network via a wireless communication 114 toan access point (AP) 140. The access point 140 communicates with anetwork controller 166 via an IP access network 150 and a securitygateway (SGW) 171. The network controller 166 monitors connectionrequests associated with each mobile device, processes each connectionrequest, and either permits or rejects access to the IP-based wirelesstelecommunications network. Access to the IP-based wirelesstelecommunications network may be controlled based on at least oneidentifier that is associated with the mobile device. The networkcontroller 166 queries a data store 168 to determine if the mobiledevice is authorized for access to the IP-based wirelesstelecommunications network. The data store includes a number of datastorage areas containing various system data that is used in theauthorization process. For example, the data store may comprise an IPaddress list 205 of Internet Protocol (IP) addresses (or “Public IPaddress”) associated with access points, a MAC address list 210 withmedia access control (MAC) addresses associated with access points, afully qualified domain name (FQDN) list 215, a subscriber list 220 thatincludes mobile device or subscriber identifiers (such as InternationalMobile Subscriber Identifiers (IMSIs)), a zone database, and other listsand databases that are not depicted but are discussed herein. As will bedescribed in additional detail, one or more of the identifiers that arestored in the data store may be utilized to determine access to thesystem. The lists may include “blocked” identifiers as well as“authorized” identifiers. The data store may also contain a subscriberhistory database 230 for purposes of service support. The data store 168may be a single database, table, list, catalog, or data structure forstorage, or a combination of such elements. Authorized accesses to theIP-based wireless telecommunications network may be maintained by thenetwork controller 166 in an authorized session table or similar dataconstruct.

FIG. 4 is a flow chart that provides further detail about how aconnection request received from a mobile device is processed in orderto either permit or reject access to the IP-based wirelesstelecommunications network. At a block 305, a connection request isreceived from a mobile device. For purposes of this description, aconnection request includes one or more communications between themobile device, access point, and service provider network withsufficient information to evidence a request by the mobile device toaccess the VoIP service. The connection request may include thecommunication of one or more of the following identifiers: (i) a mobiledevice or subscriber identifier (such as an International MobileSubscriber Identifier (MI)); (ii) a service set identifier (SSID)associated with the packets being communicated with the access point;(iii) a Cell Global Identifier (CGI) of the nearest co-extensive networkcell that can be received by the mobile device or a cached value of themost recent network cell that was detected by the mobile device; (iv) amedia access control (MAC) address associated with the access point; and(v) a public IP address and a private IP address (if assigned)associated with the access point connection to the Internet.

At a block 310, the authentication and access authorization module 172compares the mobile device or subscriber identifier received in theconnection request with the subscriber database to determine if thesubscriber is allowed access to the VoIP service and/or VoIP roamingservice. At a decision block 315, the facility determines whether theuser of the mobile device has subscribed to receive VoIP service and/orVoIP roaming service. Users who have not subscribed to receive serviceare rejected by the authentication and access authorization module andthe connection request denied at a termination block 320. For users whohave subscribed to receive service, processing continues at a block 325.

At block 325, the facility redirects the subscriber to an appropriateserving network controller (NC) 166. While a single NC element isdepicted in FIGS. 2A, 2B, and 3, it will be appreciated that typically anumber of NCs are utilized by a service provider in order to managenetwork traffic. As a result, the facility selects an appropriate NCusing such rules as assigning a default NC to the mobile device,assigning a service NC associated with the access point that is handlingthe connection request, or assigning other NCs in accordance with otherservice provider rules. Once the connection request is assigned to aserving NC, the mobile registration procedure continues at a block 330.

At block 330, the facility stores one or more of the identifiersreceived in the connection request in the subscriber history database230, including the mobile device or subscriber identifier, SSID, MACaddress, CGI, or public and private IP address identifiers. FIG. 5 is arepresentative subscriber history table 400 associated with a particularsubscriber. Each row in the subscriber history table 400 represents oneconnection request by the subscriber's mobile device. Each column in thesubscriber history table 400 represents an identifier associated withthe connection request or details of the subsequent session if theconnection request is authorized. For example, a column 405 is providedto store the mobile device or subscriber identifier (such as an IMSI), acolumn 410 is provided to store the SSID associated with the packetsbeing communicated with the access point, and a column 415 is providedto store a MAC address associated with the access point. Three columnsare provided to store information about a detected network cell,including a column 420 to store the CGI of a co-extensive network cellthat can be received by the mobile device or a cached network cell thatwas recently detected by the mobile device, a column 422 to store anindication of whether the CGI value is a live CGI (i.e., detectable bythe mobile while in communication with the access point) or a cached CGI(i.e., previously detected by the mobile prior to communication with theaccess point), and a column 424 to store an indication of the age of theCGI value if the CGI value represents a cached CGI. Additional columnsin the subscriber history table include columns 425 and 430, which storea public and private IP address associated with the access pointconnection to the Internet, and a column 435 to store a time stampassociated with when the connection request was received. Some or all ofthe data is stored in columns 405-435 of the subscriber history table400 by the facility for each connection request by the subscriber'smobile device, regardless of whether the mobile device is ultimatelyauthorized to use the VoIP service as a result of the connectionrequest. In this fashion, the facility is able to track both successfuland unsuccessful connection requests.

Additional columns are provided in the subscriber history table 400 tostore details about the VoIP session if the connection request isauthorized. A column 440 is provided to store a length of the VoIPsession. The session length may be represented by an ending time stampor by a number that reflects elapsed time (e.g., in minutes and seconds)from the time stamp associated with the connection request. A column 445is provided to store a termination code that reflects how the sessionwas ended. For example, a first code may indicate that the subscriberended the session, and a second code may indicate that the session wasdropped as a result of unacceptable delays introduced by Internetcongestion. Those skilled in the art will appreciate that thetermination codes may be expanded to include codes covering all typicaltermination events. As applicable in a converged network, column 450 isprovided to store one or more identifiers that are reflective of thecellular services that were used by the subscriber during the VoIPsession. Those skilled in the art will appreciate that additionalcolumns may be added to the subscriber history table 400 if theadditional information stored in the table might be valuable to servicesupport representatives or other troubleshooters.

Returning to FIG. 4, once the identifiers associated with the connectionrequest are stored, processing continues at a decision block 335. Atdecision block 335, the facility determines whether the CGI associatedwith the connection request has been blocked. That is, the facilitydetermines whether a live CGI associated with the connection request hasbeen deemed to be a mobile cell where VoIP service should not to beoffered. If the CGI is blocked, at a termination block 340 theconnection request is denied.

If the CGI is not blocked, processing continues to a decision block 345where the facility determines whether the MAC address associated withthe access point has been blocked. MAC addresses may be blocked for avariety of reasons, including for continuing to provide improper orinvalid subscriber information in an attempt to access the VoIP service.If the MAC address is blocked, at a termination block 350 the connectionrequest is denied.

If the MAC address is not blocked, processing continues to a block 355where the proper CGI and VoIP service zones are sent to the mobiledevice. FIG. 6 is a flow chart of a process 500 for determining theproper CGI and VoIP service zones for the mobile device. At a decisionblock 505, the facility determines whether the MAC address identified inthe connection request matches a MAC address stored in the subscriberdatabase. That is, the facility determines whether the access pointthrough which the mobile device is making the connection requestcorresponds to an access point that is operated by a subscriber. If theMAC address matches a MAC address stored in the subscriber database, ata block 510 the facility uses the CGI value and service zone that arestored in the subscriber database. The values stored in the subscriberdatabase are typically those values that were identified by the serviceprovider as part of the original process of registering the access pointto provide access to the IP-based wireless telecommunications system.

If the MAC address does not match a MAC address stored in the subscriberdatabase at decision block 505, at a block 515 the facility determinesthe service type from the subscriber database. That is, the facilitydetermines what type of service plan the subscriber has subscribed towith the service provider. The service plan selected by the subscriberwill determine what value of CGI and service zone should be selected forbilling purposes. At a block 520 the facility determines the servicezone from the service zone database. The service zone database containsgroups of known access points, IP addresses, and fully-qualified domainnames for access points that have been approved by the service provider.For example, the service zone database may contain a list of all accesspoints that are operated by the service provider at public locations.

At a decision block 525, the facility determines whether any of theservice zones apply to the service type associated with the subscriber.If there is a match between the service type and the service zone, thenat a block 530 the facility uses the CGI value and service zone from aService Type database. The Service Type database stores the relationshipbetween service types and the zones in the service zone database. Ifthere is no match between the service plan and the service zone, then ata block 535 the facility uses a default CGI value and a default servicezone as selected by the service provider. Following identification ofthe appropriate CGI value and service zone, processing continues toblock 360 of FIG. 4.

At block 360, the facility updates the CGI value that is stored in thesubscriber history table 400 if the CGI value has changed as a result ofthe outcome of process 500 for determining the proper CGI and servicezone. Updating the subscriber history table ensures that the subscriberhistory is accurately maintained for billing and service supportpurposes. At a block 365, the facility allows the mobile device toconnect to the IP-based wireless telecommunications network and receiveVoIP service.

The facility continually updates the subscriber history table 400 as thesubscriber utilizes his or her mobile device and attempts to access theservice provider's VoIP service. At the same time, the subscriberhistory is made available to service support providers to enable servicesupport representatives to assist the subscriber if the subscriber isunable to access the VoIP service or has difficulties with the VoIPservice. FIG. 7 is a screenshot of a representative application programdisplay 600 that allows a service support representative to view thesubscriber's history in order to troubleshoot problems or respond tosubscriber or other inquiries.

The service support application display is divided into three regions: asubscriber information region 605, a VoIP access summary region 610, anda detailed VoIP reporting region 615. The subscriber information region605 displays a number of pieces of pertinent subscriber information thatthe service support representative may desire to see at a glance,including the subscriber name, address, mobile telephone number, andmobile device or subscriber identifier (e.g. an IMSI number). A searchbutton 620 is provided that takes the service support representative toa search form (not shown) where the representative can search for adifferent subscriber using a variety of queries, such as by mobiledevice or subscriber identifier. A “more” button 625 takes the servicesupport representative to additional data screens associated with thesubscriber, such as a billing history screen or screens related to otherservices received by the subscriber.

The second region on the application display 600 is the VoIP accesssummary region 610. The VoIP access summary region depicts statisticalsummaries of the subscriber's connection requests over a defined period.The service support representative is allowed to define the summaryperiod by entering a date range in two date fields 630. When theapplication display is first presented to the service supportrepresentative, the date range may be a default range such as theprevious thirty day period. The number of successful VoIP servicerequests during the period in question is displayed in the accesssummary region, as are the number of unsuccessful service requests. Abutton 635 is provided next to the number of successful requests and abutton 640 is provided next to the number of unsuccessful requests.Selecting either button 635 or 640 causes the details of thecorresponding requests to be displayed in the detailed VoIP reportingregion 615. That is, selecting button 635 causes details of thesuccessful connection requests to be displayed in reporting region 615,and selecting button 640 causes details of the unsuccessful connectionrequests to be displayed in reporting region 615. Depending on thestorage capacity of the service provider systems, the amount of datastored pertaining to successful and unsuccessful requests may be limitedby the facility. For example, only the most recent twenty requests maybe stored for subsequent analysis by a service support representative. Acellular access “view” button 645 is also provided in the VoIP accesssummary region 610 that, when depressed, displays a reporting screenthat relates to the customer's attempts to access the service provider'scellular network. In this fashion, the service support representativemay quickly and easily switch between viewing the VoIP history and thecellular history of a subscriber.

The third region on the application display 600 is the detailed VoIPreporting region 615. The detailed VoIP reporting region displays a listof details about the successful service requests or the unsuccessfulservice requests, depending on whether button 635 or button 640 was lastdepressed. Each row 650 in the detailed VoIP reporting regioncorresponds to a single connection request. An event number 665 isassigned to each row so that the connection requests can be more readilydistinguished. The facility populates the details about each connectionrequest with data obtained from the subscriber history database 230. Thedisplayed data may comprise the SSID associated with each connectionrequest, the MAC address of the access point, the CGI of nearby cells,the public IP address serving the access point, and the starting timestamp and length of the session. A service support representative isallowed to view additional details about each connection request byselecting a “more” button 655 that is associated with the request.Selecting the “more” button causes additional details about theconnection request to be displayed, such as services accessed by asubscriber during a session after the request is authorized. Such datais also obtained by the facility from the customer history database.

The service support representative is provided a number of ways tomanipulate the data that is presented in the detailed VoIP reportingregion 615. A scroll control 660 is provided to allow the servicesupport representative to scroll up and down in the list of connectionrequests until a desired connection request is identified. Selecting oneof the column headings in the reporting region 615 causes the connectionrequests to be sorted in accordance with the selected heading. Forexample, selecting the heading “MAC” in the column heading causes theconnection requests to be sorted in ascending or descending order inaccordance with the MAC address associated with each connection request.Those skilled in the art will appreciate that other ways to manipulatethe displayed data, such as horizontal scroll bars, keyword searching,and other techniques may also be used by the facility. Moreover, whilethe application display 600 depicts a listing for connection requeststhat were successful and a separate listing for connection requests thatfailed, those skilled in the art will appreciate that all connectionrequest outcomes may be displayed in a single table with the outcome ofthe connection request indicated by the use of underlining,highlighting, font, colors (e.g. successful requests may be highlightedgreen and unsuccessful requests may be highlighted red), or othermarking.

Since the subscriber history database 230 is accessed on a continuingbasis, and since the service support application derives its data fromthe history database, the data that is presented to the service supportrepresentative is a timely and accurate picture of the access successesand failures being experienced by the subscriber. By aggregating all ofthe data in a single location, and by presenting data about theconnection requests that succeeded as well as failed, the servicesupport representative is provided with sufficient information to allowthe representative to troubleshoot service problems or otherwise assistthe subscriber. The disclosed facility thereby improves the overallsubscriber experience when utilizing a VoIP service. The data in thesubscriber history database may be used for other purposes as well, suchas for analyzing when an access point was first used in order to start awarranty period on the access point.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof, means any connection or coupling,either direct or indirect, between two or more elements; the coupling ofconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, shall referto this application as a whole and not to any particular portions ofthis application. Where the context permits, words in the above DetailedDescription using the singular or plural number may also include theplural or singular number respectively. The word “or,” in reference to alist of two or more items, covers all of the following interpretationsof the word: any of the items in the list, all of the items in the list,and any combination of the items in the list.

The above detailed description of embodiments of the system is notintended to be exhaustive or to limit the system to the precise formdisclosed above. While specific embodiments of, and examples for, thesystem are described above for illustrative purposes, various equivalentmodifications are possible within the scope of the system, as thoseskilled in the relevant art will recognize. For example, while processesor blocks are presented in a given order, alternative embodiments mayperform routines having steps, or employ systems having blocks, in adifferent order, and some processes or blocks may be deleted, moved,added, subdivided, combined, and/or modified to provide alternative orsubcombinations. Each of these processes or blocks may be implemented ina variety of different ways. Also, while processes or blocks are attimes shown as being performed in series, these processes or blocks mayinstead be performed in parallel, or may be performed at differenttimes. Further any specific numbers noted herein are only examples, andalternative implementations may employ differing values or ranges.

The teachings of the methods and system provided herein can be appliedto other systems, not necessarily the system described above. Theelements and acts of the various embodiments described above can becombined to provide further embodiments.

While certain aspects of the technology are presented below in certainclaim forms, the inventors contemplate the various aspects of thetechnology in any number of claim forms. For example, while only oneaspect of the invention is recited as embodied in a computer-readablemedium, other aspects may likewise be embodied in a computer-readablemedium. Accordingly, the inventors reserve the right to add additionalclaims after filing the application to pursue such additional claimforms for other aspects of the technology.

We claim:
 1. A non-transitory computer-readable medium containinginstructions that, when executed on a processor, cause the processor toimplement a method of providing a service support representative with aninterface for viewing an access history by a user of a mobilecommunication device to an IP-based wireless telecommunications network,the method comprising: receiving via one or more wireless access pointsa plurality of connection requests to access an IP-based wirelesstelecommunications network from a mobile communication device that iscapable of transmitting and receiving communications via an IP-basedwireless telecommunications network, wherein each of the plurality ofconnection requests includes one or more identifiers, wherein some ofthe plurality of connection requests result in the mobile communicationdevice failing to access the IP-based wireless telecommunicationsnetwork because the mobile device is not authorized to access theIP-based wireless telecommunications network; and wherein the mobilecommunication device is assigned an IP address when it successfullyaccesses the IP-based wireless telecommunications network; storing theone or more identifiers associated with each of the plurality ofconnection requests; storing data associated with attempts by the mobilecommunication device to access a cellular network; providing theinterface for a service support representative to view the stored one ormore identifiers associated with at least a portion of the plurality ofconnection requests and the data associated with attempts by the mobilecommunication device, wherein the requests include both a request todirectly access the cellular network and a request to indirectly accessthe cellular network through another wireless network; and allowing theservice support representative to view the stored one or moreidentifiers associated with connection requests that failed, wherein theone or more identifiers are selected from a group consisting of a mobiledevice identifier, a subscriber identifier, an International MobileSubscriber Identifier, a service set identifier, or a Cell GlobalIdentifier, and wherein another identifier is selected from a groupconsisting of a Media Access Control address, a public IP address, and aprivate IP address.
 2. The non-transitory computer-readable medium ofclaim 1, wherein the interface allows the service support representativeto view stored identifiers associated with connection requests that weregranted access.
 3. The non-transitory computer-readable medium of claim1, wherein the mobile device is not authorized to access the IP-basedwireless telecommunications network because it is associated with ablocked identifier.
 4. The non-transitory computer-readable medium ofclaim 1, wherein the method further comprises providing searchfunctionality to allow the service support representative to search theone or more identifiers.
 5. The non-transitory computer-readable mediumof claim 1, wherein the method further comprises providing filteringfunctionality to allow the service support representative to filter theone or more identifiers associated with each of the plurality ofconnection requests and the data associated with attempts by the mobilecommunication device to access the cellular network.
 6. Thenon-transitory computer-readable medium of claim 1, wherein thefiltering functionality allows the service support representative tofilter by a date range associated with the plurality of connectionrequests, and a date range of the attempts by the mobile communicationdevice to access the cellular network.
 7. The non-transitorycomputer-readable medium of claim 1, wherein the IP-based wirelesstelecommunications network is an unlicensed mobile access (UMA) network.8. The non-transitory computer-readable medium of claim 1, wherein theinterface permits use of a subscriber access history to start a warrantyperiod for an access point.
 9. The non-transitory computer-readablemedium of claim 1, wherein the interface permits updating a subscriberhistory table with new CGI values to allow for billing and supportservices.
 10. A system for providing a service support representativewith an interface for viewing an access history by a user of a mobilecommunication device to an IP-based wireless telecommunications network,the system comprising: means for receiving via one or more wirelessaccess points a plurality of connection requests to access an IP-basedwireless telecommunications network from a mobile communication devicethat is capable of transmitting and receiving communications via anIP-based wireless telecommunications network, each of the plurality ofconnection requests including one or more identifiers, wherein some ofthe plurality of connection requests result in the mobile communicationdevice failing to access the IP-based wireless telecommunicationsnetwork because the mobile device is not authorized to access theIP-based wireless telecommunications network; and wherein the mobilecommunication device is assigned an IP address when it successfullyaccesses the IP-based wireless telecommunications network; means forstoring the one or more identifiers associated with each of theplurality of connection requests; means for storing data associated withattempts by the mobile communication device to access a cellularnetwork; and means for providing the interface for a service supportrepresentative to view the stored one or more identifiers associatedwith at least a portion of the plurality of connection requests and thedata associated with attempts by the mobile communication device,wherein the requests include both a request to directly access thecellular network and a request to indirectly access the cellular networkthrough another wireless network; and allowing the service supportrepresentative to view the stored one or more identifiers associatedwith connection requests that failed, wherein the one or moreidentifiers are selected from a group consisting of a mobile deviceidentifier, a subscriber identifier, an International Mobile SubscriberIdentifier, a service set identifier, or a Cell Global Identifier, andwherein another identifier is selected from a group consisting of aMedia Access Control address, a public IP address, and a private IPaddress.
 11. The system of claim 10, wherein the mobile device is notauthorized to access the IP-based wireless telecommunications networkbecause it is associated with a blocked identifier.
 12. The system ofclaim 10, further comprising means for providing search functionality toallow the service support representative to search the one or moreidentifiers.
 13. The system of claim 10, wherein the interface permitsupdating a subscriber history table with new CGI values to allow forbilling and support services.
 14. The system of claim 10, wherein theinterface permits use of a subscriber access history to start a warrantyperiod for an access point.
 15. A method of providing a service supportrepresentative with an interface for viewing an access history by a userof a mobile communication device to an IP-based wirelesstelecommunications network, the method performed by a processorexecuting instructions stored in a memory, the method comprising:receiving via one or more wireless access points a plurality ofconnection requests to access an IP-based wireless telecommunicationsnetwork from a mobile communication device that is capable oftransmitting and receiving communications via an IP-based wirelesstelecommunications network, each of the plurality of connection requestsincluding one or more identifiers, wherein some of the plurality ofconnection requests result in the mobile communication device failing toaccess the IP-based wireless telecommunications network because themobile device is not authorized to access the IP-based wirelesstelecommunications network; and wherein the mobile communication deviceis assigned an IP address when it successfully accesses the IP-basedwireless telecommunications network; storing the one or more identifiersassociated with each of the plurality of connection requests; storingdata associated with attempts by the mobile communication device toaccess a cellular network; providing the interface, generated via theprocessor executing instructions stored in the memory, for a servicesupport representative to view the stored one or more identifiersassociated with at least a portion of the plurality of connectionrequests and the data associated with attempts by the mobilecommunication device, wherein the requests include both a request todirectly access the cellular network and a request to indirectly accessthe cellular network through another wireless network; and allowing theservice support representative to view the stored one or moreidentifiers associated with connection requests that failed, wherein theone or more identifiers are selected from a group consisting of a mobiledevice identifier, a subscriber identifier, an International MobileSubscriber Identifier, a service set identifier, or a Cell GlobalIdentifier, and wherein another identifier is selected from a groupconsisting of a Media Access Control address, a public IP address, and aprivate IP address.
 16. The method of claim 15, wherein the interfaceallows a service support representative to view stored identifiersassociated with connection requests that were granted access.
 17. Themethod of claim 15, wherein the mobile device is not authorized toaccess the IP-based wireless telecommunications network because it isassociated with a blocked identifier.
 18. The method of claim 15,further comprising providing search functionality to allow the servicesupport representative to search the one or more identifiers.
 19. Themethod of claim 15, further comprising providing filtering functionalityto allow the service support representative to filter the one or moreidentifiers associated with each of the plurality of connection requestsand the data associated with attempts by the mobile communication deviceto access the cellular network.
 20. The method of claim 15, wherein theinterface allows for updating a subscriber history table with new CGIvalues to allow for billing and support services.
 21. The method ofclaim 15, wherein the interface allows use of a subscriber accesshistory to start a warranty period for an access point.